Efficiently migrating stateful middleboxes

Migrating stateful web services using Apache Axis and P2P

Common web service architectures follow the classical client-server model with the client bound to the web service by a static physical connection. In this paper we show that this model is too restricted for some business scenarios and motivate the paradigm and the advantages of migratable web services. Migratable web services are instances of conventional web services that can change their exe...

Efficiently Migrating Lotus Notes Applications to Modern Platforms

The Liquid.js Framework for Migrating and Cloning Stateful Web Components across Multiple Devices

We are heading toward an era in which users own more than one single Web-enabled device. These devices range from smart phones, tablets and personal computers to smart Web-enabled devices found in houses and cars. The access mechanisms and usage patterns of Web applications are changing accordingly, as users interact more and more with Web applications through all their devices, even if the maj...

Migrating and Pairing Recursive Stateful Components Between Multiple Devices with Liquid.js for Polymer

With the continuous development of new Web-enabled devices, we are heading toward an era in which users connect to the Web with multiple devices at the same time. Users expect Web applications to be able to flow between all the devices they own, however the majority of the current Web applications was not designed considering this use case scenario. As the number of devices owned by a user incr...

Middleboxes No Longer Considered Harmful

Intermediate network elements, such as network address translators (NATs), firewalls, and transparent caches are now commonplace. The usual reaction in the network architecture community to these so-called middleboxes is a combination of scorn (because they violate important architectural principles) and dismay (because these violations make the Internet less flexible). While we acknowledge the...